Connecting multiple slave devices to single master controller in bus system

ABSTRACT

A device comprising: a bus master, including a bi-directional data and clock lines, configured to produce a select signal output for enabling data transmission on the bi-directional data line to first/second different data busses supporting multiple slave devices configured to receive/transmit data over a respective data bus and to receive a clock signal from the bus master from the clock line; and a de-multiplexer including an input, first and second outputs and a control input, the input coupled to the bi-directional data line of the bus master, first/second outputs of the de-multiplexer coupled to first/second data busses, respectively, and the control input configured to receive the select signal from the bus master that is configured to communicate to a first slave device when the select signal is in a first state, and a second different slave device when the select signal is in a second different state.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 13/687,044 filed Nov. 28, 2012, and entitled “Connecting Multiple Slave Devices to Single Master Controller in Bus System,” which is incorporated by reference.

BACKGROUND

This specification relates to electronic communication.

Electronic devices can communicate in accordance with a communication protocol over a communication medium. Some communication protocols require that a given device be addressed, and communications from and to the given device can include the address. Different addresses can be used to disambiguate one component from another.

SUMMARY

In general, one innovative aspect of the subject matter described in this specification can be implemented in a device that comprises: a bus master including a bi-directional data line and clock line and being configured to produce a select signal output for enabling data transmission on the bi-directional data line to first and second different data busses that support one or more slave devices, each slave device configured to receive/transmit data over a respective data bus and to receive a clock signal from the bus master from the clock line; and a de-multiplexer including an input and first and second outputs and a control input, the input being coupled to the bi-directional data line of the bus master, a first output of the de-multiplexer being coupled to the first data bus and a second output of the de-multiplexer being coupled to the second data bus. The control input is configured to receive the select signal from the bus master. The bus master is configured to communicate to a first slave device coupled to the first data bus when the select signal is in a first state, and to communicate to a second different slave device coupled to the second data bus when the select signal is in a second different state.

These and other implementations can each optionally include one or more of the following features. The bus master can be an I2C master and the slave devices can be I2C slaves. The bus master and the de-multiplexer can be incorporated in a microcontroller. The device can further include logic for coupling the bus master and de-multiplexer. The select signal can be provided on a general input/output port of the microcontroller. The slave devices can have a same address. The de-multiplexer can be a 1-2 de-multiplexer. The de-multiplexer can be a 1-2^(N) de-multiplexer where N is an integer, and each output of the de-multiplexer can be coupled to a data bus that in turn is coupled to one or more slave devices. The device can further comprise a second de-multiplexer including an input and first and second outputs and a control input, the input being coupled to the bi-directional clock line of the bus master, a first output of the second de-multiplexer being coupled to a first clock bus and a second output of the second de-multiplexer being coupled to a second clock bus. The first and second clock busses can be coupled to one or more slave devices associated with the first and second data busses respectively, and the control input can be configured to receive the select signal from the bus master.

In general, another innovative aspect of the subject matter described in this specification can be implemented in a master device for communicating with two or more different slave devices over a single bus, the single bus including a data bus and a clock bus, the improvement comprising: coupling the data bus from the master device to an input of a de-multiplexer and respective outputs of the de-multiplexer to different slave devices using different data busses; and configuring the master device to control the de-multiplexer to select one of the different data busses associated with a respective one of the different slave devices depending upon which slave device is desired to be communicated with.

In general, another innovative aspect of the subject matter described in this specification can be implemented in a microcontroller. The microcontroller includes a master device including a data line and a clock line and being configured to produce a select signal output for enabling data transmission on the data line to first and second different data busses of the microcontroller that support one or more slave devices, each slave device configured to receive/transmit data over a respective data bus and to receive a clock signal from the master controller from the clock line. The microcontroller further includes a de-multiplexer including an input and first and second outputs and a control input, the input being coupled to an output of the data line of the master device, a first output of the de-multiplexer being coupled to the first data bus and a second output of the de-multiplexer being coupled to the second data bus. The control input is configured to receive the select signal from the master device. The microcontroller further includes logic coupling the master device, the de-multiplexer and output pads of the microcontroller that correspond to the first and second data busses. The master device is configured to communicate to a first slave device coupled to the first data bus when the select signal is in a first state, and to communicate to a second different slave device coupled to the second data bus when the select signal is in a second different state.

These and other implementations can each optionally include one or more of the following features. Logic in the microcontroller can include a first buffer coupling a first output of the de-multiplexer to a first pad associated with the first data bus of the microcontroller. Logic in the microcontroller can include a second buffer coupling a second output of the de-multiplexer to a second pad associated with the second data bus of the microcontroller, and an AND gate having first and second inputs and an output coupled to an input of the data line of the master device. Logic in the microcontroller can include a third buffer coupling the first pad of the microcontroller to the first input of the AND gate. Logic in the microcontroller can include a fourth buffer coupling the second pad of the microcontroller to the second input of the AND gate.

In general, another innovative aspect of the subject matter described in this specification can be implemented in a method comprising: providing a data bus from a master device to an input of a de-multiplexer and respective outputs of the de-multiplexer to different slave devices using different data busses; and configuring the master device to control the de-multiplexer to select one of the different data busses associated with a respective one of the different slave devices depending upon which slave device is desired to be communicated with.

Particular embodiments of the subject matter described in this specification can be implemented so as to realize none, one or more of the following advantages. Multiple I2C devices can be coupled to a single master device in a communication network, even where two or more of the devices share the same address. Methods and apparatus are proposed to enable two slave devices that share a common address to communicate with a single master, such as by using multiple busses, one for each of the slave devices. By utilizing a multi-bus configuration, bus loading and limitations regarding the same address can be minimized.

Utilizing a multi-bus configuration can enable a reduction in the strength of the clock signal and/or data signal pull-up resistors (e.g., data signal only when the clock signal is common) required and can therefore reduce the power needed for communication. As an example, moving from 2.2 kiloohms to 4.7 kiloohms for the pull-up resistors can reduce the power loss of the clock signal by more than 2. When multiple devices are being distributed on two different busses, pull-up resistors can be weaker since capacitive load of each bus is reduced; and the same bus speed can be achieved.

Further, a multi-bus architecture does not require designers to duplicate software (e.g., to enable handling another master), or use software emulation (e.g., bit-banging of the master). This can save development time when writing the firmware for an application, and memory space, e.g., through use of mutually shared software code.

The details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example microcontroller for communicating with two different slave devices.

FIG. 2 is a diagram of an example microcontroller for communicating along two different data busses.

FIG. 3 is a diagram of an example microcontroller for communicating along two different data and clock busses.

FIG. 4 is a diagram of an example signal timeline for controlling data transmission to two slave devices each coupled to respective buses using a clock and a bus select signal.

FIG. 5 is a schematic of an example microcontroller using a de-multiplexer, logic and buffers for communication with plural slave devices.

Like reference numbers and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a diagram of an example microcontroller 100 for communicating with two different slave devices 104 a and 104 b. In the present example, the slave devices 104 a-104 b can be inter-integrated circuit (I2C) slave devices (or some other two-wire interface slave devices) having the same slave address. The slave devices 104 a-104 b may have been assigned the same address at or coincident to a time of manufacture, as might be the case when the devices are configured prior to delivery to a customer. The slave devices 104 a-104 b can be produced by a same manufacturer, or different manufacturers. While reference is made to two slave devices 104 a-104 b, more than two can be included in the environment. Two devices have been shown for clarity purposes only.

Microcontroller 100 includes a microcontroller unit (MCU) 102 that includes software components 114 and hardware components 116. The MCU 102 can include first and second data lines and a clock line. Slave device 104 a, for example, can be coupled to the first data line of the MCU 102, over which a data signal 0 106 a is received. Slave device 104 a can be further coupled to the clock line of the MCU 102, over which a clock signal 108 is received. Similarly, slave device 104 b can be coupled to the second data line of the MCU 102 (e.g., over which a data signal 1 106 b is received) and to the clock line of the MCU 102 (e.g., over which clock signal 108 is received).

The configuration of components of the microcontroller 100, for example, enables data transmission to each of the two different slave devices 104 a and 104 b, even when the two slave devices have the same slave address. For example, software components 114 and hardware components 116 can control signals that are sent across the data signals lines 106 a-106 b and the clock signal 108 so that communication can occur with an appropriate slave device and at an appropriate time.

In some implementations, clock signal line 108 and data signal lines 106 a and 106 b are coupled to resistors 110 a-110 c (e.g., pull-up resistors), which are in turn coupled to voltage sources 112 a-112 b. Other components and configurations can be used to create hard high or hard low signals on the data and clock signal lines as required for a given communication protocol.

FIG. 2 is a diagram of an example microcontroller 200 for communicating along two different data busses. For example, the microcontroller 200 can allow communication with two slave devices having the same address.

The microcontroller 200 includes a microcontroller unit (MCU) 202 that is configured to act as a master device (e.g., an I2C bus master). The MCU 202 includes a data line 220, a clock line 218, and a select signal output 222. MCU 202 is configured to enable data transmission on the data line 220 to first and second different data busses 204 a and 204 b. For example, data busses 204 a and 204 b of the microcontroller 200 can support one or more slave devices (e.g., I2C slave devices). Each of the data busses 204 a and 204 b is configured to receive/transmit data over a respective data bus. Clock line 218 of the MCU 202 is used to transmit a clock signal to each of the respective slave devices. In some implementations, the select signal output 222 can be a general input/output port of the MCU 202. The MCU 202 can produce a select signal and provide it on select signal output 222 to control selection of one of a plurality of data buses coupled to the MCU 202. The control of the data buses enables plural different slave devices to be coupled to the MCU 202 (one on each bus) even where the slave devices have a common address.

The microcontroller 200 further includes a de-multiplexer 210 having an input 224, first and second outputs 226 a-226 b, and a control input 228. The input 224 is coupled to the output of the data line 220 of the MCU 202. The first output 226 a of the de-multiplexer 210 is coupled to the first data bus 204 a, e.g., carrying data signal 0 (SDA0) 206 a. The second output 226 b of the de-multiplexer 210 is coupled to the second data bus 204 b, e.g., carrying data signal 1 (SDA1) 206 b. The control input 228 is configured to receive the select signal 216 from the MCU 202 via the select signal output 222.

In some implementations, buffers can be used to couple the MCU 202, the de-multiplexer 210 and output pads of the microcontroller that correspond to the first and second data busses (e.g., busses 204 a and 204 b). The MCU 202 can communicate with a first slave device coupled to the first data bus (e.g., data bus 204 a) when the select signal 216 is in a first state. When the select signal 216 is in a second different state, the MCU 202 is configured to communicate to a second different slave device coupled to the second data bus (e.g., data bus 204 b).

FIG. 3 is a diagram of an example microcontroller 300 for communicating along two different data and clock busses. The microcontroller 300 is similar to the microcontroller 200 described with reference to FIG. 2, except that the microcontroller 300 includes a de-multiplexer 310 for creating two separate clock signals. The de-multiplexer 310 receives the same bus select signal 216 that is received by the de-multiplexer 210. As a result, the de-multiplexer 310 produces SCL0 clock signal 0 208 a when the select signal 216 is in a first state. The SCL0 clock signal 0 208 a is received by bus 0 204 a. When the select signal 216 is in a second different state, the de-multiplexer 310 produces SCL1 clock signal 1 208 b. The SCL1 clock signal 1 208 b is received by bus 1 204 b.

FIG. 4 is a diagram of an example signal timeline 400 for controlling data transmission to two slave devices each coupled to respective buses using a clock and a bus select signal. For example, the signal timeline 400 shows a data exchange on bus 0 204 a and bus 1 204 b between the MCU and two slave devices which may have the same slave address (e.g., a 7-bit address of 0x5B). As such, the signal timeline 400 represents an example set of signals that can occur using the microcontroller system 200 described with respect to FIG. 2. For example, the signal timeline 400 includes a bus select signal 402 that can correspond to signals that occur on the bus select line 216. SDA0 signal line 404 and SDA1 signal line 406 can correspond, for example, to signals on the SDA0 line 206 a and SDA1 line 206 b, respectively. SCL signal line 408 can correspond, for example, to clock signals described above.

Times T₀ 410 through T₁₄ 410 a are example times in the signal timeline 400 at which certain events occur, e.g., corresponding to transmission of data to/from slave devices 0 and 1. For example, at time T₁ 410 a, bus select signal 402 is set low, and SDA0 signal line 404, SDA1 signal line 406 and SCL signal line 408 are set high.

At time T₁ 410 a, a start (“S”) high-to-low signal is sent on the SDA0 signal line 404 (e.g., sent to slave device 0), signaling that data transmission is commencing. The signal is received by the first slave device (slave device 0) that is coupled to the SDA0 signal line, for example, because the bus select line 402 is low, a state in which data can be received on the SDA0 signal line 404. Thereafter, MCU 202 can produce the clock signal, e.g., a clock generator associated with the MCU 202 can begin to send alternating high and low signals on the SCL signal line 408. As such, sampling of data on the SDA0 signal line 404 can begin.

At time T₂ 410 b, on an upward, low-to-high edge of the clock signal, a “1” value can be read from the SDA0 signal line 404. In the example, shown, a single data rate protocol is used. Other rates can be used, including a double data rate in which sampling occurs on both the rising and falling edges of the clock cycle.

At times T₃ 410 c, T₄ 410 d and T₅ 410 e, the next data values (e.g., values “0”, “1” and “1”) can be read from the SDA0 signal line 404. Additional data values can be read, finishing with the final value (e.g., a “1” value) that is read from the SDA0 signal line 404 at time T₆ 410 f. This completes the data transfer to the first slave device (slave device 0) that is coupled to the first data bus (e.g., as represented by the SDA0 signal line 404 in this sequence).

At time T₇ 410 g, a write (“W”) signal is generated, followed by an acknowledgement (“A”) signal at time T₈ 410 h. At time T₉ 410 i, a stop (“P”) signal is generated. As data transmission has ended, the clock generator can stop sending clock signals over the SCL signal line 408 (as shown in the break in the clock signal generation at times T₉-T₁₁. The signaling protocol described is an example of a signaling protocol that can be used to communicate, such as between a master and a slave device that is coupled as shown with reference to FIGS. 2 and 3. Other protocols can be used.

At approximately time T₁₀ 410 j, the MCU 202 can cause the bus select signal 402 to transition from low to high, enabling communication to the second slave device (slave device 1) that is coupled to the second data bus. After the transition, communication using SDA0 signal line 404 is disabled, and communication using SDA1 signal line 406 is enabled. At time T₁₁ 410 k, a start (“S”) high-to-low signal can be provided on the SDA1 signal line 406 (e.g., sent by MCU 202 to slave device 1), signaling that data transmission is to commence. The clock generator in the MCU 202 can resume sending clock signals, enabling data to be read from bus 1 over the SDA1 signal line 406.

At time T₁₂ 410 l, a write (“W”) signal is generated (e.g., meaning that the master wants to write to the slave), followed by an acknowledgement at time T₁₃ 410 m. At time T₁₄ 410 n, a stop (“P”) signal is generated (by MCU 202) signaling a release of the respective bus. Thereafter, the clock generator stops sending clock signals over the SCL signal line 408. Pursuant to the write signal at time T₁₂ 410 l, no data is written since the communication is stopped at that time. This kind of frame can be used, for example, to probe a component on the bus, e.g., “if ACK, then the device is present; if NACK, then the device is not present.”

FIG. 5 is a schematic of an example microcontroller 500 using a de-multiplexer, logic (e.g., an AND gate) and buffers for communication with plural slave devices. For example, pads 502 a and 502 b can be connected to different slave devices (e.g., I2C slave devices). The logic in the microcontroller 500 makes it possible for a master device 504 to interface with different slave devices even if they have the same address. While two pads 502 a and 502 b are shown in this example of the microcontroller 500, other configurations can allow for more pads (e.g., four, eight, sixteen, etc.), enabling the microcontroller 500 to control a corresponding number of slave devices, even where those slave devices have a common address.

As depicted, the microcontroller 500 is an example in which a bus master (e.g., master device 504) and a de-multiplexer (e.g., the de-multiplexer 508) are incorporated in a single device. For example, some or all of the components of the microcontroller 500 can be contained in silicon, e.g., rather than having some components external to the master device 504. In some implementations, the components can be included in the bus master, or included in silicon with the bus master.

In some implementations, the microcontroller 500 includes plural buffers. For example, a first buffer 514 a couples a first output 512 a of a de-multiplexer 508 (e.g., a 1-2 de-multiplexer) to the first pad 502 a associated with the first data bus of the microcontroller. A second buffer 514 b couples a second output 512 b of the de-multiplexer 508 to a second pad 502 b associated with the second data bus of the microcontroller.

In the configuration shown, logic (e.g., AND gate 520 having first and second inputs 520 a and 520 b and an output 524) has inputs coupled to the first and second pads 502 a and 502 b, respectively, through third and fourth buffers 518 a and 518 b, respectively. The output of the AND gate 520 is coupled to an input 506 a of the master device 504. An output 506 b of the master device 504 is coupled to the de-multiplexer 508.

In some implementations, the de-multiplexer 508 can be a 1-2^(N) de-multiplexer (where N is an integer), and each output of the de-multiplexer 508 can be coupled to a data bus that in turn is coupled to one or more slave devices. For example, if N is 2, then de-multiplexer 508 can be a 1-4 de-multiplexer. In some implementations, the logic of the microcontroller 500 can be modified to replace the two-input AND gate 522 with an AND gate having the same number of 2^(N) inputs (or with plural gates). The number of buffers, in addition to buffers 514 a, 514 b, 518 a and 518 b, would also increase proportionally.

While reference is made above to communications flowing from the MCU to the slave devices, transmission from the slave devices to the MCU is also contemplated. The example communication sequence was used to highlight the protocol required to successfully communicate with the two different slave devices using the configurations shown. Other sequences are possible. Similarly, the example communication protocol described is associated with I2C devices and includes start and stop signals and a read/write bit. The configurations shown enable plural I2C slave devices to communicate with a single master device. Other communication protocols can be used. While reference is made to slave devices being assigned a same address, this is not strictly required. For example the multiple bus architecture can be used even where slave devices do not have a common address. Such a multiple-bus architecture can be used to minimize bus loading, such as when many slave devices are included in a given implementation.

Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).

The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. 

What is claimed is:
 1. A device comprising: a bus master including a bi-directional data line and clock line and being configured to produce a select signal output for enabling data transmission on the bi-directional data line to first and second different data busses that support one or more slave devices, each slave device configured to receive/transmit data over a respective data bus and to receive a clock signal from the bus master from the clock line; and a de-multiplexer including an input and first and second outputs and a control input, the input being coupled to the bi-directional data line of the bus master, a first output of the de-multiplexer being coupled to the first data bus and a second output of the de-multiplexer being coupled to the second data bus, wherein the control input is configured to receive the select signal from the bus master; wherein the bus master is configured to communicate to a first slave device coupled to the first data bus when the select signal is in a first state, and to communicate to a second different slave device coupled to the second data bus when the select signal is in a second different state.
 2. The device of claim 1 wherein the bus master is an I2C master and the slave devices are I2C slaves.
 3. The device of claim 1 wherein the bus master and the de-multiplexer are incorporated in a microcontroller.
 4. The device of claim 3 further including logic for coupling the bus master and de-multiplexer.
 5. The device of claim 1 wherein the select signal is provided on a general input/output port of the microcontroller.
 6. The device of claim 1 wherein the slave devices have a same address.
 7. The device of claim 1 wherein the de-multiplexer is a 1-2 de-multiplexer.
 8. The device of claim 1 wherein the de-multiplexer is a 1-2^(N) de-multiplexer where N is an integer and wherein each output of the de-multiplexer is coupled to a data bus that in turn is coupled to one or more slave devices.
 9. The device of claim 1 further comprising a second de-multiplexer including an input and first and second outputs and a control input, the input being coupled to the bi-directional clock line of the bus master, a first output of the second de-multiplexer being coupled to a first clock bus and a second output of the second de-multiplexer being coupled to a second clock bus, wherein the first and second clock busses are coupled to one or more slave devices associated with the first and second data busses respectively, and wherein the control input is configured to receive the select signal from the bus master.
 10. A microcontroller including: a master device including a data line and clock line and being configured to produce a select signal output for enabling data transmission on the data line to first and second different data busses of the microcontroller that support one or more slave devices, each slave device configured to receive/transmit data over a respective data bus and to receive a clock signal from the master controller from the clock line; a de-multiplexer including an input and first and second outputs and a control input, the input being coupled to an output of the data line of the master device, a first output of the de-multiplexer being coupled to the first data bus and a second output of the de-multiplexer being coupled to the second data bus, and wherein the control input is configured to receive the select signal from the master device; and logic coupling the master device, the de-multiplexer and output pads of the microcontroller that correspond to the first and second data busses; wherein the master device is configured to communicate to a first slave device coupled to the first data bus when the select signal is in a first state, and to communicate to a second different slave device coupled to the second data bus when the select signal is in a second different state.
 11. The microcontroller of claim 10 wherein the logic includes: a first buffer coupling a first output of the de-multiplexer to a first pad associated with the first data bus of the microcontroller; a second buffer coupling a second output of the de-multiplexer to a second pad associated with the second data bus of the microcontroller; an AND gate having first and second inputs and an output coupled to an input of the data line of the master device; a third buffer coupling the first pad of the microcontroller to the first input of the AND gate; and a fourth buffer coupling the second pad of the microcontroller to the second input of the AND gate.
 12. A method comprising: providing a data bus from a master device to an input of a de-multiplexer and respective outputs of the de-multiplexer to different slave devices using different data busses; and configuring the master device to control the de-multiplexer to select one of the different data busses associated with a respective one of the different slave devices depending upon which slave device is desired to be communicated with. 